Out of the Box Rules
An ‘Out of the Box’ Rule as the name suggests is a pre-packaged or pre-developed rule that just needs some minimal information to be set-up and validate quality on certain aspects.
Out of Box Rules are Only available as Business Rules and can be created during the normal create flow either separately or together with another custom rule.
Each ‘Out of the Box’ rule corresponds to an exception condition which the rule validates. Currently Fluree Sense provides for the following OOB rules:
| OOB Rule | Exception Condition |
|---|---|
| Must be Populated or Non-Null | Value is null |
| Must be of the defined data type | value is not of data type selected in drop-down in OOB screen. |
| Must have a valid value from the Referenced data list | Value is within (dataset details provided in OOB screen) |
| Must be a Unique value | Frequency is greater than 1 |
| Must come Before | Is greater than - Threshold value provided in OOB screen ( Date related) |
| Must come After | Is less than – Threshold value provided in OOB screen (Date related) |
| Must be Equal To | is not equal to – numerical threshold value |
| Must be Greater Than | Is less than or equal to – numerical threshold value |
| Must be Less Than | Is greater than or equal to |
| Must Not Be a Statistical Outlier | z-score is greater than 3 |
OOB Rules integration with Resolve
OOB rules are integrated with the Resolve product , if that is licensed along with Classify. The rules that we set up on Concepts (or Entity Attributes as we call them in Resolve), appear there in the ‘Define Data Quality Rules’ screen for an Entity. This has been discussed in detail in this section of Resolve.
Let us also touch upon a special Out of the Box rule: ‘Must have a valid value from the Referenced Data list’.
This rule allows the user to ask for validation that all the values of the concept are from a specific list – This list can be composed of a distinct list made up of columns and we’ll just see how.
The next screen shows how the rule’s Reference Data is set-up in 6 quick steps after we click the edit pencil icon to create this OOB rule.
System Validations
-
There can be one OOB rule of a specific type on a concept. For this reason, cloning is disabled for OOB rules and the OOB rule condition becomes disabled the moment it is created – which is on the press of the Next Step button on that screen.
-
You can only edit the Description of OOB rule in edit mode – even when you’re the Rule Admin. Since OOB rules are for a specific predefined reason and have pre-defined exception conditions, you cannot change these aspects and its name, dimensions etc.
-
Some OOB rules are only visible in the OOB screen (as seen above) if the Data corresponds to a specific Data Type. For example – Must Come Before and Must Come After will not appear if the DataType of the concept is not DateTime.
-
If you have the Resolve product, these OOB rules appear in the Resolve product as the existing defined Data Quality rules on Entities.
-
The rule for Referenced Data has additional validations such as:
-
The drop-downs in the opened pop-up are dependent on each other and the Data sources, Data Sets filter to the ones for which the user has at least Read rights
-
The Apply Changes button only gets enabled if there is at-least one row for the Reference Data List (but there can be more than one)
-
Once the changes are applied, they show up in the OOB rule screen but can still be edited from there before ‘Next Step’ is pressed in the parent screen. Once ‘Next Step’ is pressed, the rule is created (as is the convention for OOB rules).